|
Screenshot
Demonstration of Hudson running in browser |
|
| Stable release | 2.1.1 / August 30, 2011 |
|---|---|
| Written in | Java |
| Operating system | Cross-platform |
| Type | Continuous integration |
| License | MIT license |
| Website | hudson-ci.org |
| As of | August 30, 2011 |
Hudson is a continuous integration (CI) tool written in Java, which runs in a servlet container, such as Apache Tomcat or the GlassFish application server. It supports SCM tools including CVS, Subversion, Git and Clearcase and can execute Apache Ant and Apache Maven based projects, as well as arbitrary shell scripts and Windows batch commands. The primary developer of Hudson was Kohsuke Kawaguchi, who worked for Sun Microsystems at the time. Released under the MIT License, Hudson is free software.[1] The Hudson project is supported by Oracle Corporation.
Builds can be started by various means, including scheduling via a cron-like mechanism, building when other builds have completed, and by requesting a specific build URL.
During recent years Hudson has become a popular alternative to CruiseControl and other open-source build servers.[2][3] At JavaOne conference in May 2008, it was the winner of Duke's Choice Award in Developer Solutions category.[4]
Contents |
Plugins have been released for Hudson, extending it far beyond purely being a build tool for Java projects. Plugins are available for integrating Hudson with most version control systems and bug databases. Many build tools are supported via their respective plugins. Plugins can also change the way Hudson looks or add new functionality. Builds can generate test reports in various formats (JUnit is supported out-of-the-box, others via plugins) and Hudson can display the reports and generate trends and render them in the GUI.
During November 2010, an issue arose in the community of Hudson with respect to the infrastructure used, which grew to encompass questions over Oracle's stewardship and perceived control of the project.[5] Negotiations between the principal project contributors and Oracle took place, and although there were many areas of agreement a key sticking point was the control of the name "Hudson" itself, which Oracle claimed, and for which it submitted a trademark registration in early December 2010 (not granted as of February 2011).[6] As a result, on January 11, 2011, a proposal was made to change the project name from "Hudson" to "Jenkins".[7] The proposal was overwhelmingly approved by those that voted on January 29, 2011, creating the Jenkins project.[8] On February 1, 2011, Oracle indicated that they, in partnership with others in the community intended to continue development of Hudson making the necessary infrastructure changes, confirming two development branches.[9] Both the Jenkins and Hudson projects appear to consider the other to be a fork.
On May 3, 2011, the Eclipse Foundation in conjunction with the key Hudson committers, Oracle, Sonatype and other community supporters put forward a formal proposal[10] for the transfer of Hudson, including the core code and problematic trademarks to the Eclipse Foundation. Hudson's founder Kohsuke Kawaguchi saw the Oracle move as validating Jenkins. "When we were talking with Oracle to find a middle ground, they made it very clear that they have no intention of giving up the trademark control. But with this move, they clearly acknowledge that Oracle couldn't keep up with the Jenkins project." [11] He also questioned whether Oracle could legally reassign copyright and relicense all the Hudson intellectual property as part of the move to Eclipse.